3-3 Create "Floor Plans"

These drawings show proposed console, rack, and equipment locations within the client's room specifications. The main purpose of these drawings is to establish the names of the rooms, as well as the names and location of racks and console bays used within each room, (e.g., A room called Edit 1 may contain Rack 1, Rack 2, and Bays 1 through 4.) Small systems--such as Flight Cases and small Select Systems--may not necessarily require Floor Plans, but if any Floor Plans are created, they must be sent to the client for sign-off.

Create "Rack and Console Elevations"

These drawings show where devices will be mounted in consoles and racks. It is very important that Elevation drawings indicate the device mnemonic, make, and model, (e.g., VT 1, Sony, DVW-500.) The router control system programming is typically the limiting device for creating device mnemonics. These drawings must also indicate the inputs on all monitoring equipment, as well as note-area information on patch panels so that the client can visualize the operation of the depicted areas. Send drawings to client for signoff and indicate a specific date to return the signed drawings to Engineering.

Note: At this point we have the "big picture" of what the system is all about: The Project Definition Phase is Done. Now you are prepared to begin the Detailed System Design Phase.

Logic of Bay and Rack Numbering

There is a preferred numbering scheme for racks and bays. When multiple rooms are involved, it is suggested that each room be given a block of numbers. The block size should consider the present quantity of both racks and bays plus allowing for future expansion. For example, there are three edit suites with five bays and seven racks in each. A possible scheme is to use numbers 1 to 19 for Edit Suite 1 racks and bays, 20 to 39 for Edit Suite 2, and 40 to 59 for Edit Suite 3. This numbering scheme gives each rack and bay a unique number and reserves numbers for future expansion.

Each rack and bay should be given a unique number based on the block of numbers assigned to the room where it is located. Racks could use the lower half of the room block numbers and bays the upper half. When assigning mnemonics to individual bays and racks, do not repeat mnemonic suffix numbers. For example: once BAY 1 has been used, Bay 1 or Rack 1 cannot be used again in another place. Following this logic; if there are seven racks and five bays in Edit Suite 2, the racks might be numbered RK 21 through 27 and the bays in that room would be numbered BAY 31 through 35. This approach makes it easy for the client to associate equipment numbers with specific rooms. For example: BAY 33 exists in only one place - Edit Suite 2.

Like mnemonics, the rack and bay numbering scheme is negotiable and subject to client modification and/or approval.. There could be additional SIC labor required to accommodate rack and bay numbering schemes that deviate from the standard SIC schemes described here. The numbering example in Figure 9 is an excerpt from a small installation and demonstrates a variation on the scheme previously described. Note the bay and rack numbers are not repeated in the rooms shown, but the rack and bay numbers are sequential. Separate blocks of numbers were not used for bays and racks. The customer wanted the numbering done this way.

Summary of Bay Numbering

• Find out the max number of bays in each specific room and add a future expansion fudge factor. Assign blocks of bay numbers to each room as previously explained. If number blocks have already been assigned to the racks, bay number blocks should follow the logical sequence.
• When assigning mnemonics to individual bays, do not repeat mnemonic suffix numbers in different rooms. Once BAY 1 has been used, BAY 1 or RK 1 cannot be used again.
• Include known future bays in dotted lines and assign them numbers as if they were present. Example: present bays may be named BAY 1-5 and BAY 6 may be designated as "future."e;
• Space permitting, include an appropriate general statement about the bay that helps illustrate its purpose. For example: "Mixer and ADAs." This additional information is invaluable as a catalyst for customer discussions.
• Be consistent in the logic used. Establish a mnemonic assignment and bay layout approach and use it for all bays in all rooms. Summary of Rack Numbering
• Find out the max number of racks in each specific room and add a fudge factor for future expansion. Then assign predictably numbered blocks (ranges) of racks to each room. Example: MASTER CONTROL 1 may have RACKs 11-16 (and Bays 21-28) and MASTER CONTROL 2 may have RACKs 31-36 (and Bays 41- 48).
• Do not repeat suffix numbers in different rooms. Once RK 1 has been used, BAY 1 or RK 1 cannot be used again.
• Number rack rows left to right in ascending order as seen from the front (knobs side).
• Include known future racks in dotted lines and assign them numbers as if they were present. Example: present racks may be named RK 1-7 and RK 8 may be designated as “future.”
• Space permitting, include an appropriate general statement about the rack that helps illustrate its purpose. For example: “Router and VDAs.” This additional information is invaluable as a catalyst for customer discussions.

Logic of Room Naming

Be consistent and use Arabic number suffixes (not letters) so text and numbers alternate. For example: EDIT 2 RK 1 are recognizable as two mnemonics even if the spacing accidentally runs them together. Don’t use EDIT A one place and then AUDIO 1 down the hall. Number every room involved in the project even if there is currently only one (e.g., MCR 1 not just MCR) - another (MCR 2) could be added later. Only number rooms with which SIC is involved. Creating mnemonics for storage rooms and bathrooms is unnecessary.

Design Considerations

• Ergonomics - Layout room, rack, and console locations with general people flow, tape flow, and operator traffic efficiency in mind. Minimize the distance people will have to travel to accomplish their daily tasks. For example: the tape library should be located near the VTR racks or the Library Management System.
• Serviceability - Equipment maintenance is important to placement of racks in a room. In rooms where space is available leave 20 to 24 inches of space behind the racks for maintenance purposes. If a minimum of 20 inches of space cannot be left behind the racks, extended service cable loops should be used to allow equipment maintenance from the front. Extended service cable loops allow racks to be placed against a wall to maximize usable operations space.
  Consider cabling density when choosing which equipment will be placed in racks against walls. Equipment like routers and patch bays that have very high cable density should not be placed in racks against walls if it can be avoided. Equipment with low density cabling (like monitors and audio speakers) is better suited to this type of installation.
• Signal Limitations - Many interface/control cables have line length limits. Keep edit suites close to the machine room to keep control cables short or include special control cable extension hardware.

Creating Rack and Console Elevations

Rack and Console Elevations combined with the Floor Plan provide the client and operations staff with the first opportunity to see where the racks and consoles are in relation to a room (and each other) and to visualize what it will be like to work with that equipment design. User friendly ergonomics is a top priority in rack and console design.

The client (and hopefully the operations staff) must approve these plans before design and system construction can begin. This is the customer’s opportunity to make changes (early in the project’s life). Once signed off, the elevation drawings are frozen. Changes to signed off elevation drawings that have a significant functional or financial consequence require change order negotiations between SIC project management and the client before implementation.

Excel rack elevations are very handy for faxing or e-mailing because of their compact size. They are often used as legitimate electronic and hard copy interchange with clients to obtain comments and approval in the project’s early design stage. Client comments and signatures made on Excel rack elevations should be photocopied for use by Engineering and the original delivered to Document Control.

Design Considerations

The main goal is to achieve a functional AND ergonomic balance in the design. Consider the following: Is the work area for operators comfortable? Is equipment in the most sensible place and grouped logically? Can a technician work on the equipment? Is there room for future expansion? Will the equipment fail prematurely due to blocked vents or fans?

• Equipment density: The project Installation Supervisor should be consulted in cases of exceptional density; especially in patch bays and router frames.
• Cooling: Spread out major heat generating devices. Scopes and monitors with CRTs usually generate considerable heat and need air flow. Consider the depth of adjacent units. Air flow can be significantly increased by strategically placing shallow devices to expose adjacent unit air vents and create breathing room. Use blank panels only after attempting to utilize shallow devices first. Units that suck air from the front panel or from the bottom should not be located near the floor where dust is likely to clog fan intakes or blanket the internal boards and components.
• Blank Panels: Don’t get too specific about the installation of blank panels. For example: if there is a 3RU space, don’t specify on the rack elevation drawing that a single RU blank be placed above a 2RU blank. Just specify a 3RU space and let Implementation figure out the best way to fill it.
• Seismic Bracing: Drawings with instructions for the project Installation Supervisor should be provided in unusual situations such as train, truck, boat, and airplane installations. Some cities, counties, and states may also have building codes that require seismic bracing for racks above a certain height.
• Device Locations: Equipment that doesn’t have a lot of user adjustments (set once and forget it) goes at the top and bottom of racks. Switcher and router electronics, DAs, sync generators, and change-overs are typical examples. When possible, place the heaviest equipment at the bottom.

Locate devices in the racks with signal flow in mind; keep cables short as possible. The project Installation Supervisor should be consulted early during rack layout in cases of unusually high density cabling.

Equipment that is constantly being adjusted and monitored should be easily accessible. Place quality control (QC) equipment (e.g., monitor, waveform, vectorscope, router control panel, and intercom station) together and at a comfortable adjustment and viewing level (around sitting or standing eye level).

It follows to place adjustable equipment (e.g., a TBC control panel) next to the QC station. Units such as VTRs should be placed at a comfortable height for frequent tape loading and unloading.

Future Expansion

Racks

Leave at least 20% extra space in each rack to allow future equipment additions. Reserve spaces by placing blank panels in the areas where expansion is most likely to occur. Strategically placed blank panels will allow the ergonomics and functionality of the layout logic to be maintained down the road when the expansion actually takes place.

Frames

When an entire DA frame is near capacity or becomes filled, plan room in the same rack or a nearby rack for an additional DA frame.

Patch Panels

• Allow additional rack space for at least 25 percent patch panel expansion. Reserve rack space by placing blank panels in the space below the existing jackfields so patch cords can hang down without covering other equipment.
• Leave 20% of the patches in existing patch panels available for additions. Distribute the unused patches among areas most likely to experience expansion.
• Bring unused picture monitor, waveform monitor, vectorscope, etc., inputs to patch. If all inputs are used, at least one should be patchable.

Labeling Rack Mounted Devices

The philosophy behind rack elevation device labeling is to convey as much information as possible in the limited space available. The mnemonics used should be taken from the Mnemonics List if it is done (see Section 3.5.4.). Devices that use 2 rack units (2RU) or less only have space for the device mnemonic, make, and model. Larger units afford more typing space so additional information can be added in the form of a signal description (name of signal the device carries), equipment description, and/or an equipment note. Figure 11 demonstrates the use of descriptions and notes to provide additional device information.

Labeling Monitors

Video and waveform monitors need to show the signal sources available for viewing. MON 1 in Figure 11 is an example of input selector button labeling. Show the input selector button names exactly as they appear on the device front panel. To indicate button programming, use the official project mnemonic of the selectable device and (if space is available) a one word descriptor for its purpose. Unused selector buttons are labeled "NC" but are always shown.

The button labeling convention just described is unique to rack elevations. Here the "front panel" button labels are used to indicate to an operator how the monitor input selector buttons have been programmed. On video synoptics, inputs are labeled with the "physical connector" name as shown on the device I/O panel to tell the Installer or Maintenance Tech how the device should be cabled.

Sight Line Drawings

Console elevations should always include sight line drawings. Side views like Figure 14 are commonly used. Overhead views may also be employed when appropriate. Such drawings help the client ascertain ergonomic attributes of the console design. They also prompt SIC engineers to double-check equipment placement within the racks. Create "Switcher," "Mixer," "Router I/O Lists."

Create these Input/Output (I/O) lists on separate Excel worksheets and send to the client right away for approval and sign-off. They describe all of the signal inputs and outputs of each of these important devices, (e.g., The router Input 1 may be Black, Input 2 Cam 1, or Input 3 Cam 2. The router Output 1 may be VTR 1 or Output 2 VTR 2.)Assign mnemonics for all I/O signals. These mnemonics must fit the device control system programming restrictions, remote control panel operation, LED display limitations, and were summarized in the Abbreviations List. These I/O lists describe the operational functionality of the system in a very succinct way.